post /mint/organizations/{org_name}/transaction-search
Gets transaction activity for the specified organization using the specified criteria. See also Reporting transaction activity using the API.
HTTP request
Path Parameters
org_name (required) | Organization name. |
Query Parameters
all |
Flag that specifies whether to return all records. If set to |
size |
Number of records returned per page. If the |
page |
Number of the page that you want to return (if content is paginated). If the |
Request Body
Criteria used to search for transactions.
appCriteria | ID and organization for a specific application to be included in the report. If this property is not specified, all applications are included in the report. | |||||
| ||||||
billingMonth | Billing month of the report, such as Note: This property is not valid for revenue reports. | |||||
billingYear | Billing year for the report, such as Note: This property is not valid for revenue reports. | |||||
currCriteria | ID and organization for a specific currency to be included in the report. If this property is not specified, all supported currencies are included in the report. | |||||
| ||||||
currencyOption | Currency for the report. Valid values include:
Note: If you select | |||||
devCriteria | Developer ID or email address, and organization name for a specific developer to be included in the report. If this property is not specified, all developers are included in the report. | |||||
| ||||||
devCustomAttribute | Custom attributes to include in the report, if defined for a developer. Note: This property is not valid for revenue reports. Do not specify the predefined | |||||
fromDate | Starting date and time of the report in UTC time. For example: Note: This property applies only to revenue and variance reports. | |||||
groupBy | Order in which sections are grouped in the report. Enter the values in the desired order: | |||||
monetizationPackageIds | ID of one or more API packages to include in the report. If this property is not specified, all API packages are included inthe report. Note: This property is not valid when viewing transaction activity ( | |||||
pkgCriteria | ID and organization for a specific API package to be included in the report. If this property is not specified, all API packages are included in the report. This property can be specified instead of the Note: This property is not valid when viewing transaction activity ( | |||||
prevFromDate | Starting date of a previous period in UTC. Used to create a report for a previous period for comparison against a current report. Note: This property applies only to variance reports. | |||||
prevToDate | Ending date of a previous period in UTC. Used to create a report for a previous period for comparison against a current report. Note: This property applies only to variance reports. | |||||
prodCriteria | ID and organization for a specific API product to be included in the report. If this property is not specified, all API products are included in the report. This property can be specified instead of the Note: This property is not valid when viewing transaction activity ( | |||||
productIds | ID of one or more API products to include in the report. If this property is not specified, all API products are included in the report. API product IDs should be specified as | |||||
pricingTypes | Pricing type of rate plan to be included in the report. Valid values include:
| |||||
ratePlanLevels | Type of rate plan to be included in the report. Valid values include:
If this property is not specified, both developer-specific and standard rate plans are included in the report. | |||||
showEntityId | Flag that specifies whether the reports shows the entity ID. | |||||
showRevSharePct | Flag that specifies whether the report shows revenue share percentages. | |||||
showSummary | Flag that specifies whether the report is a summary. | |||||
showTxDetail | Flag that specifies whether the report shows transaction level details. Note: This property applies only to revenue reports. | |||||
showTxType | Flag that specifies whether the report shows the type of each transaction. | |||||
toDate | Ending date and time of the report in UTC time. For example: | |||||
transactionStatus | Status of transactions to include in the report. Valid values include:
| |||||
transactionCustomAttributes | Custom transaction attributes to include in summary revenue reports. You must enable this feature in your organization. See Including custom transaction attributes in revenue summary reports. | |||||
transactionTypes | Type of transactions to be included in the report. Valid values include: |
Response Types
200:
OK
Body
totalRecords | Total number of records. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
transaction | Details of the transactions. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|